From: Keir Fraser <keir.fraser@citrix.com>
Date: Mon, 22 Mar 2010 10:29:42 +0000 (+0000)
Subject: No cpu_add_remove_lock in do_boot_cpu.
X-Git-Tag: archive/raspbian/4.8.0-1+rpi1~1^2~12492
X-Git-Url: https://dgit.raspbian.org/%22http://www.example.com/cgi/success//%22http:/www.example.com/cgi/success/?a=commitdiff_plain;h=5bc8ad3bb763c0c0d3f0676e586838a1d478fb51;p=xen.git

No cpu_add_remove_lock in do_boot_cpu.

The do_boot_cpu() will be called when system booting or CPU
online. When system booting, we don't need hold this lock. When system
online, the lock is held already by cpu_up.

Signed-off-by: Jiang, Yunhong <yunhong.jiang@intel.com>
---

diff --git a/xen/arch/x86/smpboot.c b/xen/arch/x86/smpboot.c
index 98f2c1155c..fcac97419a 100644
--- a/xen/arch/x86/smpboot.c
+++ b/xen/arch/x86/smpboot.c
@@ -985,10 +985,8 @@ static int __devinit do_boot_cpu(int apicid, int cpu)
 		cpucount--;
 
 		/* Mark the CPU as non-present */
-		spin_lock(&cpu_add_remove_lock);
 		x86_cpu_to_apicid[cpu] = BAD_APICID;
 		cpu_clear(cpu, cpu_present_map);
-		spin_unlock(&cpu_add_remove_lock);
 	} else {
 	}